Ignore the other pyo3 RUSTSEC advisory - #8460
Conversation
Signed-off-by: Adam Gutglick <adam@spiraldb.com>
Merging this PR will not alter performance
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | encode_varbin[(1000, 2)] |
158.3 µs | 177.2 µs | -10.63% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[128] |
215.3 ns | 186.1 ns | +15.67% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[1024] |
275.6 ns | 246.4 ns | +11.84% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing adamg/rustsec-advisory-ignore-20260617 (a5365e6) with develop (170ff39)
Footnotes
-
10 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
## Summary Follow up to #8381, another pyo3 issue. Signed-off-by: Adam Gutglick <adam@spiraldb.com>
2 participants
Summary
Follow up to #8381, another pyo3 issue.